Release 10.1A: OpenEdge Development:
Web Services

CHARACTER or LONGCHAR

Table D–1 describes the supported castings in each 4GL parameter mode (INPUT and OUTPUT) between the 4GL CHARACTER or LONGCHAR type and XML Schema.

Table D–1: 4GL data type cast—CHARACTER or LONGCHAR 

For this XML Schema type...	In this 4GL parameter mode...	OpenEdge...
All XML Schema types where CHARACTER is the suggested 4GL mapping (see Chapter 8 "Analyzing WSDL for Progress 4GL Access to Web Services").	INPUT1	Attempts to format the 4GL string value to match the specified XML Schema type for inclusion in the SOAP request message.2
	OUTPUT1	Converts the value from the formatting of the specified XML Schema type before copying it into the 4GL parameter as a string value.2
All XML Schema types where CHARACTER or LONGCHAR is not the suggested 4GL mapping (see Chapter 8 "Analyzing WSDL for Progress 4GL Access to Web Services").	INPUT1	Copies the string value directly, with no attempt to format it, for inclusion in the SOAP request message. OpenEdge performs minimal validation to ensure that the string contains data formatted according to the rules of the XML Schema type.
	OUTPUT1	Copies the XML Schema value directly from the SOAP response message to the 4GL parameter unchanged from its XML Schema format.

1On both INPUT and OUTPUT parameters, OpenEdge translates the value between the cpinternal code page and Unicode. 2The process of serializing and de-serializing CHARACTER data inserts and removes XML character references, for example, replacing "<" with "&lt;".